OpenEdge Development: <br />Web Services Errors occurring in Web service application requests

A Web service application request is initiated by a client, which creates a SOAP message and sends it to the WSA. The WSA processes the SOAP message, creates a response, and sends the response back to the client. An error can occur on the client side or the server side.

Client-side errors

A client-side error occurs before the request is sent or while it is being processed by the WSA.

An example of an error occurring before the request is sent is a mismatch in interface parameters. For these types of errors, the type of client response depends on the client platform.

Examples of errors occurring while the request is being sent (which involve a session-managed AppServer application) include:

Forgetting to call the connect method first.

Not sending the correct Object ID in the SOAP header.

Web server not running.

Web service URL incorrectly specified (host or port).

Network down.

Using HTTP instead of HTTPS when required.

Server-side errors

A server-side error occurs while the request is being processed by the WSA and the error is not related to the contents of the SOAP request. Examples of server-side errors include:

Forgetting to enable a specific deployed Web service.

Forgetting to enable client access to Web services for the WSA instance.

Configuring or starting an AppServer incorrectly. This might involve one or more of the following issues:

Invalid Propath on the AppServer.

Invalid AppService (Application Service name).

Incompatible AppServer operating mode for the Web service session model.

Missing 4GL, or an incorrect version of the 4GL.

Configuring the Java Servlet Engine (JSE) incorrectly so it does not recognize the WSA).